On 11/7/2015 9:25 PM, TK
tk@...
[DynoMotion] wrote:
Hi Sam,
It certainly would be unacceptable to always require
booting with driver signature disabled.
But I asked you to perform a procedure since you did a
fresh install of W10 with all updates. I can't tell
if you read or tried the procedure to install the
drivers how we normally do. Please clearly indicate
if you have or not and what happened.
Actually you might also need to uninstall the driver.
Then boot with signature checking disabled. Then
power KFLOP. Then Install the driver in response to
New Hardware found.
I think you may be mixing the instructions you gave me in
another email thread (from before I clean reinstalled
Windows 10) and this thread (after I clean reinstalled
windows 10). To clarify, here is what I have done:
-I booted into "Signature Checking Disabled" mode. UAC is at
it's most minimum setting. It cannot be fully disabled in
Windows 10 without serious issues.
-I uninstalled the KFLOP driver in the Device manager by
right-clicking Uninstall on the KFLOP-Motion Controller 4.xx
icon. After accepting the warning dialog, it vanishes.
-I then deleted the ftd2xx.dll (for the heck of it) from the
system32 folder.
-I uninstalled the KMotion 433q package in Control Panels,
Programs & Features.
-I turned the KFLOP off and rebooted normally.
At this point my machine should be free of everything
KFlop-related.
-I then rebooted into "Signature Checking Disabled" mode.
-I powered up the KFlop. There is no "New Hardware Found"
dialog; nothing appears on screen. There is a "ding" sound,
so it was found.
-After a moment, the "KFLOP - Motion Controller 4.XX" icon
appears in the Universal Serial Bus Controllers section of
the Device Manager. The icon is normal. There is *no* ftd2xx
dll in the system32 folder. I ran my app, and it runs fine,
controlling the KFlop normally. At this point I have NOT
unstalled the KMotion 433q package.
-Now I install the KFlop 433q package (deselecting the Mach3
Plugin). It installs without error. I test ran the
Dynomotion.net, KMotionCNC and KMotion apps without
incident.
I'm guessing at this point that the similarity with the
previous (before installing Windows 10 from scratch)
incident is that the ftd driver is still failing to install
into system32.
-So, I did a manual install of the KFLOP.inf file in the
c:\KMotion433q by right-clicking the icon and selecting
Install. A dialog appears saying that installation was
successful. The ftd2xx.dll now appears in the System32
folder.
-I did a manual install of the KMotion.inf file in the same
manner. A dialog appears saying that installation was
successful.
-I again tested Dynomotion, KMotionCNC and my app. All
continue to function normally.
-I powered down the KFlop.
I then rebooted normally.
-After login, I powered up the KFlop. The "KFlop - Motion
Controller 4.xx" icon appears in the Device Manager, but now
it has a yellow exclamation point triangle over the icon.
The ftd2xx.dll is still present in the system32 folder.
Attempting to run KMotion's Console/Version command returns
"Can't Connect to KMotion Board #0".
I reboot back into "Signature Checking Disabled" mode.
-All KMotion apps and my app run normally.
I reboot normally.
-KMotion version returns "Can't Connect to KMotion Board
#0".
Am I missing a possible installation step anywhere that
could cause this issue?
sam marrocco | chief technical officer
ringside.cutters.flavor.picnic.moonlink
248 548 2500 w
248 910 3344 c
ringsidecreative.com
